HPAVC

home *** CD-ROM | disk | FTP | other *** search

/ HPAVC / HPAVC CD-ROM.iso / pc / GENCSRC.ZIP / COMPILER.DOC < prev next >

Wrap

Text File | 1987-11-21 | 32.0 KB | 880 lines

Coronado Enterprises C TUTOR Nov 21, 1987 COMPILER.DOC file Notes on a few C compilers. It is assumed that you have a C compiler and that you have somehow learned to use it. Some helping hints are given below for some of the more popular compilers and even if your partic- ular compiler is not listed, some of the hints given for other compilers may help you with yours. Some standards do tend to exist within compilers and compiler writers tend to do things basically the same way. If notes are not given below about your compiler, we at Coronado Enterprises will be unable to help. We have listed notes on all of the compilers we have available for evaluation or use. These notes are not intended to be exhaustive or used as the basis for a final decision on your part to select a given compiler. Exhaustive notes and evaluations are given regularly in computer publications. If you are undecided as to which compiler you should use, you are directed to these. ****************************************************************** The following compilers have been tested on all files in chapters 1 through 13 and the results are noted. 1. Borland Turbo C - Version 1.00 This compiler may be the best available at the price. It is certainly worth the price to purchase it for learning the language. It is extremely flex- ible and easy to use once it is set up properly on your com- puter. Follow the notes below to set it up since the users guide is extremely confusing concerning setup. 2. Computer Innovations C86 compiler version 2.30J This is a very large but capable compiler that you should have a hard disk to use. It is about two years old at this writing but a newer version should be available with even more capability. 3. Ecosoft C compiler - ver 3.14 This compiler sells for only $59.95 and is as complete a compiler as you can find if you only need a small memory model. Their small model uses 64K for program and another 64K for data, so the limitation is not very severe, and this compiler should meet nearly all of your needs. 4. Lattice C compiler - version 3.00 This is a very capable compiler that still has the ability to be run conveniently with only two floppy disks. If you want a high end compiler to use on a dual floppy machine, this is probably your best choice. The documentation is nearly worthless, and you will be left with a mess trying to get it set up until you gain some experience programming in C. 5. Mark Williams Let's C Version 3.0.2 This is a relatively inexpensive compiler that makes only a small memory model, but is certainly adequate for learning to program in C. This version is rather old and has been updated, but this is the only copy available for test and evaluation at this time. 6. Microsoft C compiler - version 3.0 7. Microsoft C compiler - version 4.0 8. Microsoft C compiler - version 5.0 These three compilers are absolutely top of the line compilers and would make an excellent choice if you will be engaged in very serious programming. The only difference in the three are the number of features available, but any of them would be excellent for use in learning to program in C. Version 4.0 and 5.0 have codeview available and version 5.0 allows the "modern" method of function definitions. All three compile to very fast, compact code but any of the three should be used only with a hard disk, since floppy disk use would require much disk swapping. 9. Microsoft Quick-C - version 1.00 This is an excellent com- piler that should do everything you ever need to do short of a full commercial development project. It is extrememly fast compiling and running, and the only thing that seems to be missing is the optimization that the Optimizing C compiler does. It is very easy to use and is well worth the price. 10. Mix C Compiler ver 1.0.0 Mix has been advertising a newer version of this compiler for only $19.95 and although it has some limitations, it would be excellent for learning to program in C. ************** Borland Turbo C - version 1.00 ********************** Borland International 4585 Scotts Valley Drive Scotts Valley, CA 95066 Due to the ease of use of the Integrated Environment version of Turbo C, It will be used exclusively by this tutorial. You can use the Command Line version of Turbo C with this tutorial, but all notes in the tutorial will describe use of the Integrated Environment version. All of the files in the Coronado Enterprises Turbo C tutorial are designed to work with the Turbo C compiler with all options left in the default mode (ie - the way the compiler comes from the factory), and any changes may affect the way some of the example programs work. *** Turbo C ****** Suggested Hard Disk Setup ********************* The Turbo C User's Guide has complete instructions describing how to set up your system for proper use. Following the direc- tions given will result in the following directory setup if you are using a hard disk. Some of the files have been omitted in this suggested setup to reduce the clutter in the TURBOC directory. This will reduce the confusion over extra files as you work your way through the tutorials. Turbo C disk 1 - INTEGRATED DEVELOPMENT ENV. Turbo C disk 2 - COMMAND LINE/UTILITIES Turbo C disk 3 - HEADER FILES/LIBRARIES/EXAMPLES Turbo C disk 4 - LIBRARIES/EXAMPLES C:\TURBOC\ TC.EXE /* From Turbo C disk 1 */ TCCONFIG.TC /* You make this file - See below */ TCHELP.TCH /* From Turbo C disk 1 */ *.* /* From Turbo C Tutor SOURCE disk */ C:\TURBOC\INCLUDE\ *.H /* From Turbo C disk 3 */ C:\TURBOC\INCLUDE\SYS\ STAT.H /* From Turbo C disk 3 \SYS\ subdir.*/ C:\TURBOC\LIB\ *.OBJ /* From Turbo C disk 3 */ *.LIB /* From Turbo C disk 3 */ *.OBJ /* From Turbo C disk 4 - optional */ *.LIB /* From Turbo C disk 4 - optional */ The *.OBJ and *.LIB files from disk 4 are needed only if you wish to use additional memory models. You only need the "Small" memory model to run all of the programs included in the Coronado Enter- prises C tutorial. After creating the subdirectories listed above and loading them with the files listed, change to the TURBOC directory and create the TCCONFIG.TC file by following these instructions (note that the instructions are given on page 16 of the Turbo C User's guide but they are somewhat cryptic for the beginner). 1. TC<return> This loads the TURBO-C compiler 2. O Selects "Options" 3. E Selects "Environment" 4. I Selects "Include directories" 5. \TURBOC\INCLUDE<return> Sets directory for include files 6. L Selects "Library directory" 7. \TURBOC\LIB<return> Sets directory for library files 8. <Esc> Returns to "Options" menu 9. S Selects "Store options" 10. <return> Stores file named "TCCONFIG.TC" 11. <Esc> Return to the TURBO-C main menu To run your first program. (This assumes FIRSTEX.C has been copied into the \TURBOC\ directory from the tutorial SOURCE disk.) 1. TC<return> Loads the Turbo C compiler 2. F Selects "Files" 3. L Selects "Load" 4. <return> Lists all files *.C 5. Position cursor on FIRSTEX.C 6. <return> Loads FIRSTEX.C 7. Alt-R Compiles and runs FIRSTEX *** Turbo C **** Suggested Dual Floppy Disk Setup ***************** The Turbo C User's Guide has very sketchy information on how to set up the system for use from two floppies so the following information is given to get you started. As you gain experience with the C lan- guage, you can add features and move files around to make it more convenient to use. The setup given here will result in the source files and executable files residing on drive B. You will develop a more convenient system soon, but this setup will get you started. You will find that you will have to stop often and erase the *.OBJ and the *.EXE files that are generated by Turbo C or your disk will fill up with these extra files. Format a disk with the system on it (ie - FORMAT A:/S) and put the following files on it for your drive A disk. TC.EXE /* From Turbo C disk 1 */ TCCONFIG.TC /* You make this file - see below */ TCHELP.TCH /* From Turbo C disk 1 */ /* Note - You will probably have */ /* room for an AUTOEXEC.BAT file on */ /* this disk also. */ Format a disk without the system, make the following directories on it, and add the following files to it in their respective dir- ectories. This will be the disk for drive B. You will put a few of the source files from the Coronado Enterprises tutorial on this disk in the root directory. \ *.C /* From the Turbo C Tutor SOURCE disk */ \INCLUDE\ *.H /* From Turbo C disk 3 */ \INCLUDE\SYS\ STAT.H /* From Turbo C disk 3 */ \LIB\ COS.OBJ /* From Turbo C disk 3 */ CS.LIB /* From Turbo C disk 3 */ EMU.LIB /* From Turbo C disk 3 */ FP87.LIB /* From Turbo C disk 3 */ MATHS.LIB /* From Turbo C disk 3 */ After creating the disks as listed above, install the disks in drive A and drive B and boot up the computer on drive A. You must then create the TCCONFIG.TC file by following these instruc- tions (note that the instructions are given on page 14 of the Turbo C User's guide but they are somewhat cryptic for the beginner). 1. TC<return> This loads the TURBO-C compiler 2. O Selects "Options" 3. E Selects "Environment" 4. I Selects "Include directories" 5. B:\INCLUDE<return> Sets directory for include files 6. O Selects "Output directory" 7. B:\<return> Sets directory for output files 8. L Selects "Library directory" 9. B:\LIB<return> Sets directory for library files 10. <Esc> Returns to "Options" menu 11. S Selects "Store options" 12. <return> Stores file named "TCCONFIG.TC" 13. <Esc> Return to the TURBO-C main menu 14. F Selects the "File" menu 15. L Selects the "Load" submenu 16. B:*.C<return> Selects the B drive for files 17. <Esc> Return to the "File" menu 18. <Esc> Return to the TURBO-C main menu Note that steps 14 through 16 must be performed once each time the Turbo C system is started to tell the system where to find the working files. To run your first program. (This assumes FIRSTEX.C has been copied into the root directory from the tutorial SOURCE disk.) Load the two disks into the computer and boot up the system. 1. TC<return> Loads the Turbo C compiler 2. F Selects "Files" 3. L Selects "Load" 4. B:*.C<return> Lists all files *.C 5. Position cursor on FIRSTEX.C 6. <return> Loads FIRSTEX.C 7. Alt-R Compiles and runs FIRSTEX *** Turbo C ***** Suggested Single Floppy Disk Setup **************** In order to use the Turbo C compiler with a single floppy disk, set up two disks as noted for the Dual Floppy Disk system. Use the disk designated for drive A above to boot up the computer and perform steps 1 through 13 given above, leaving off the drive designation for drive B in steps 5, 7, 9, and 16. To run the system, use the disk designated for drive A for booting and loading the TC system, then install the other disk as the work- ing disk. You will have all of the capabilities of the dual drive system except for the "HELP" facility and the ability to run an oper- ating system shell from within the Turbo C Integrated environment. ********** Computer Innovations C86 compiler version 2.30J ******* Computer Innovations Inc. 980 Shrewsbury Ave, Suite 310, Tinton Falls, NJ 07724 All files were put into a single directory along with the files from the Coronado Enterprises SOURCE disk to compile and run the example C programs. A batch file "CC.BAT" is provided as an aid to compile and run the example programs. Comments on running the example C programs Chapter 5 SCOPE.C - Prototyping is not supported, so this program will not compile. BACKWARD.C - Prototyping is not supported. FLOATSQ2.C - Prototyping is not supported. Chapter 6 ENUM.C - Enumerated types are not supported by this compiler. Chapter 9 SINGLEIO.C - getch() not supported. BETTERIN.C - getch() not supported. Chapter 11 STRUCT2.C - Structure assignment is not supported so remove line 22. STRUCT3.C - Remove line 29 and 30. UNION1.C - The bytes have ff in high order bits if the MSB of the byte is on. Refer to text about this. Chapter 13 BITOPS.C - The bytes have ff in high order bits if the MSB of the byte is on. Chapter 14 None of the programs in this chapter were compiled with the Computer Innovations C86 C compiler. ************** Ecosoft C compiler - version 3.14 ******************** Ecosoft Inc. 6413 N. College Ave Indianapolis, IN 46220 (recommended setup) Exactly as listed in the manual - The documentation is excellent and very clear. Only the hard disk setup was tested. (start of batch file used - CCL.BAT) IF EXIST %1 GOTO ERROR CED %1.C CC %1 IF ERRORLEVEL 1 GOTO CLERR %1 ERASE %1.EXE ERASE %1.OBJ ERASE %1.BAK GOTO DONE :ERROR REM DO NOT INCLUDE THE .C EXTENSION PAUSE GOTO DONE :CLERR REM COMPILE OR LINK ERROR PAUSE :DONE (end of batch file used) Required changes for use with Ecosoft C compiler - ver 3.14 Note; During compilation of a few of the files you will get a small number of warnings. These warnings are obvious and are meant to be an aid to you in discovering possible errors in your code. One of the most obvious is when a floating point number is assigned to an integer. This is done as an illustration for you, but the compiler generates a warning and continues. The fact that this happens is a positive vote for this compiler. You should set the "picky bit" to 9 while you are running these programs to get used to the compilers elaborate warnings. Chapter 11 - UNION1.C The bytes have ff in the high order bits if the MSB is on. Refer to text about this. Chapter 11 - BITFIELD.C This compiler does not support bitfields. Chapter 12 - All three files. Add the line #include "malloc.h" to the beginning of each file. This will define the type of return malloc will generate and will allow the pro- grams to operate as described. Ecosoft is very picky about the constructs used, and requires the header to check for problems. Chapter 13 - BITOPS.C The bytes have ff in the high order bits if the MSB is on. Refer to text about this. Chapter 14 - None of these files have been compiled with this com- piler. ************** Lattice C compiler - version 3.00 ******************** Lattice Incorporated 2500 S. Highland Ave. Lombard, IL 60148 Note; The following suggested setup only uses the small memory and program model which is sufficient for nearly all of your programming needs. It is suggested that you simply use this configuration and as you gain experience with C, add some of the other features. (suggested floppy disk setup) Contents of Drive A COMMAND.COM CCL.BAT (as listed below) EDIT.COM (your editor, whatever you use) STDIO.H (From the Lattice disks) DOS.H (From the Lattice disks) CTYPE.H (From the Lattice disks) *.C (the files you wish to compile) CS.OBJ (From the Lattice disks) Contents of Drive B LC1.EXE (From the Lattice disks) LC2.EXE (From the Lattice disks) LINK.EXE (must be IBM version 2.1 or later) LCMS.LIB (From the Lattice disks) LCS.LIB (From the Lattice disks) (suggested hard disk setup) Put all above files in one directory, and remove the references to drive B in the batch file below. (start of batch file CCL.BAT) REM C COMPILER, LATTICE VERSION 3.00 IF EXIST %1 GOTO EXTERR REM THE NEXT LINE CALLS WHATEVER SCREEN EDITOR YOU USE EDIT %1.C B:LC1 %1 IF ERRORLEVEL 1 GOTO P2ABT B:LC2 %1 IF ERRORLEVEL 1 GOTO WAIT REM THIS IS THE C LINKER B:LINK CS+%1,%1,NUL,B:LCMS+B:LCS; IF ERRORLEVEL 1 GOTO LKERFND REM THE NEXT LINE IS THE EXECUTION CALL %1 PAUSE ERASE %1.EXE ERASE %1.OBJ ERASE %1.BAK GOTO DONE :EXTERR REM YOU PROBABLY INCLUDED THE .C EXTENTION, DO NOT INCLUDE IT REM IT WILL CAUSE THE LINKER STEP TO FAIL PAUSE GOTO DONE :LKERFND REM LINK ERROR(S) FOUND PAUSE GOTO DONE :P2ABT REM PASS 2 ABORTED DUE TO PASS 1 ERRORS PAUSE GOTO DONE :WAIT REM PASS 2 ERROR(S) FOUND PAUSE :DONE ( end of batch file used ) The following problems were found when using the Lattice C compiler (version 3.00) on the files included on this disk. Chapter 5 - FLOATSQ.C Warning 85: function return value mismatch This appears to be a bug in the compiler but it doesn't affect the operation of the program. Chapter 11 - NESTED.C Add the following line as the first line of the program to increase the internal stack size. int _stack = 4000; Chapter 11 - UNION1.C The bytes have ff in high order bits if the MSB of the byte is on. Refer to text about this. Chapter 13 - BITOPS.C The bytes have ff in high order bits if the MSB of the byte is on. Note that none of the programs in chapter 14 have been run with this compiler. The programs with prototyping, and the programs ENUM.C, and BITFIELDS.C have not been run with this compiler. ************* Mark Williams Let's C Version 3.0.2 ***************** Mark Williams Co. 1430 West Weightwood Ave Chicago, IL 60614 All files were put into a single directory along with the files from the Coronado Enterprises SOURCE disk to compile and run the example C programs. rem batch file used with this compiler edit %1.c (or whatever editor you use) cc -f %1.c %1 pause erase %1.bak erase %1.exe erase %1.o rem end of batch file Comments on running the example C programs with Let's C Chapter 5 SCOPE.C - Prototyping is not supported, so this program will not compile. BACKWARD.C - Prototyping is not supported. FLOATSQ2.C - Prototyping is not supported. Chapter 9 SINGLEIO.C - getch() not supported. BETTERIN.C - getch() not supported. Chapter 11 UNION1.C - The bytes have ff in high order bits if the MSB of the byte is on. Refer to text about this. Chapter 13 BITOPS.C - The bytes have ff in high order bits if the MSB of the byte is on. Chapter 14 None of the programs in this chapter were compiled with the Mark Williams Let's C compiler. ******************** Microsoft Version 3.00 ************************* Microsoft Corporation Box 97017 Redmond, WA 98073 (recommended setup) Exactly as listed in the manual - The documentation for this compiler is very clear, and if you follow the instructions as given by Micro- soft, you will have no problem configuring your system. (start of batch file used ) IF EXIST %1 GOTO NOEXT EDIT %1.C MSC %1; IF ERRORLEVEL 1 GOTO ERROR LINK %1; IF ERRORLEVEL 1 GOTO ERROR %1 PAUSE ERASE %1.EXE ERASE %1.OBJ ERASE %1.BAK GOTO DONE :NOEXT REM DO NOT INCLUDE THE .C EXTENSION PAUSE GOTO DONE :ERROR REM COMPILE OR LINK ERROR FOUND PAUSE :DONE ( end of batch file ) Note; The above batch file assumes a hard disk is being used. Required changes for use with Microsoft C ver 3.0 Chapter 5 - SCOPE.C This compiler does not support the "modern" method of function definition. Remove the reserved word "void" from within the parentheses on lines 26, 34, and 44. Chapter 5 - BACKWARD.C This compiler does not support the "modern" method of function definition. Remove the variable names from line 5 and change line 18 to the "classical" method of function definition. Chapter 5 - FLOATSQ2.C This compiler does not support the "modern" method of function definition. Ignore this file since it is the same as FLOATSQ.C with "modern" function definitions. Chapter 6 - ENUM.C You will get a couple of warnings that you can ignore. Chapter 10 - READTEXT.C Apparently the system clears the buffer before reading into it, so it only outputs an extra blank line instead of the word "lines." as described in the text. Chapter 11 - NESTED.C *** STACK OVERFLOW *** This message occurs during running of the program due to a lack of stack space because nearly every C compiler defaults to a stack size of 2048 bytes. To fix it, change the LINK call to LINK %1 /STACK:4000; for this program only. Chapter 11 UNION1.C The bytes have ff in high order bits if the MSB of the byte is on. Refer to text about this. Chapter 13 BITOPS.C The bytes have ff in high order bits if the MSB of the byte is on. Chapter 14 All programs Change to the "classical" method of function definitions. Chapter 14 LIST.C & LISTF.C Removing all references to the print file pointer "print_file_point" and using the standard predefined pointer "stdprn" for all print operations causes immediate print rather than bufferred print. The LIST.EXE on the distribution disk uses the standard pointer. The method of printing in the files is used by most C compilers, but the standard method may be a part of the upcoming ANSI standard. Chapter 14 VC.C, FILE.C, DATA.C, VIDEO.C, and STRUCT.DEF Remove all references to "prtfile" and use "stdprn" in lines 123 and 135 of VC.C and in line 170 of FILE.C to cause immediate printing instead of delayed buffered printing. The VC.EXE on the distribution disk was done this way and was compiled with the MS 3.00 C compiler. You can use the files as is if you don't mind the funny printing method. Note; To link VC.EXE use link vc+data+file+video; ******************** Microsoft Version 4.00 ************************* Microsoft Corporation Box 97017 Redmond, WA 98073 (recommended setup) Exactly as listed in the manual - The documentation for this compiler is very clear, and if you follow the instructions as given by Micro- soft, you will have no problem configuring your system. (start of batch file used ) IF EXIST %1 GOTO NOEXT EDIT %1.C MSC %1; IF ERRORLEVEL 1 GOTO ERROR LINK /CO %1; IF ERRORLEVEL 1 GOTO ERROR %1 PAUSE ERASE %1.EXE ERASE %1.OBJ ERASE %1.BAK GOTO DONE :NOEXT REM DO NOT INCLUDE THE .C EXTENSION PAUSE GOTO DONE :ERROR REM COMPILE OR LINK ERROR FOUND PAUSE :DONE ( end of batch file ) Note; The above batch file assumes a hard disk is being used. Required changes for use with Microsoft C ver 4.0 Chapter 5 - SCOPE.C This compiler does not support the "modern" method of function definition. Remove the reserved word "void" from within the parentheses in lines 26, 34, and 44. Chapter 5 - BACKWARD.C This compiler does not support the "modern" method of function definition. Remove the variable names from line 5 ans change line 18 to the "classical" method of function definition. Chapter 5 - FLOATSQ2.C This compiler does not support the "modern" method of function definition. Ignore this file since it is the same as FLOATSQ.C with "modern" function definitions. Chapter 6 - ENUM.C You will get a warning that you can ignore. Chapter 10 - READTEXT.C Apparently the system clears the buffer before reading into it, so it only outputs an extra blank line instead of the word "lines." as described in the text. Chapter 11 - NESTED.C *** STACK OVERFLOW *** This message occurs during running of the program due to a lack of stack space because nearly every C compiler defaults to a stack size of 2048 bytes. To fix it, change the LINK call to LINK /CO %1 /STACK:4000; for this program only. Chapter 11 UNION1.C The bytes have ff in high order bits if the MSB of the byte is on. Refer to text about this. Chapter 13 BITOPS.C The bytes have ff in high order bits if the MSB of the byte is on. Chapter 14 LIST.C & LISTF.C Removing all references to the print file pointer "print_file_point" and using the standard predefined pointer "stdprn" for all print operations causes immediate print rather than bufferred print. The LIST.EXE on the distribution disk uses the standard pointer. The method of printing in the files is used by most C compilers, but the standard method may be a part of the upcoming ANSI standard. Chapter 14 VC.C, FILE.C, DATA.C, VIDEO.C, and STRUCT.DEF Remove all references to "prtfile" and use "stdprn" in lines 123 and 135 of VC.C and in line 170 of FILE.C to cause immediate printing instead of delayed buffered printing. The VC.EXE on the distribution disk was done this way and was compiled with the MS 3.00 C compiler. You can use the files as is if you don't mind the funny printing method. Note; To link VC.EXE use link vc+data+file+video; ******************** Microsoft Version 5.00 ************************* Microsoft Corporation Box 97017 Redmond, WA 98073 (recommended setup) Exactly as listed in the manual - The documentation for this compiler is very clear, and if you follow the instructions as given by Micro- soft, you will have no problem configuring your system. (start of batch file used ) EDIT %1.C CL /Zi /Od %1.C IF ERRORLEVEL 1 GOTO ERROR %1 PAUSE ERASE %1.EXE ERASE %1.OBJ ERASE %1.MAP ERASE %1.BAK GOTO DONE :ERROR REM COMPILE OR LINK ERROR FOUND PAUSE :DONE ( end of batch file ) Note; The above batch file assumes a hard disk is being used. Required changes for use with Microsoft C ver 5.00 Chapter 10 - READTEXT.C Apparently the system clears the buffer before reading into it, so it only outputs an extra blank line instead of the word "lines." as described in the text. Chapter 11 - NESTED.C *** STACK OVERFLOW *** This message occurs during running of the program due to a lack of stack space because this compiler defaults to a stack size of 2048 bytes. To fix it, use these commands; C>CL /c NESTED.C C>LINK NESTED /STACK:4000; C>NESTED Chapter 11 UNION1.C The bytes have ff in high order bits if the MSB of the byte is on. Refer to text about this. Chapter 13 BITOPS.C The bytes have ff in high order bits if the MSB of the byte is on. Note; None of the programs in chapter 14 have been compiled with this compiler. ************* Microsoft Quick-C version 1.00 ******************** Microsoft Corporation Box 97017 Redmond, WA 98073 Required changes for use with Microsoft Quick-C ver 1.0 Chapter 10 - READTEXT.C Apparently the system clears the buffer before reading into it, so it only outputs an extra blank line instead of the word "lines." as described in the text. Chapter 11 - NESTED.C *** STACK OVERFLOW *** This message occurs during linking of the program due to a lack of stack space because this compiler defaults to a stack size of 2048 bytes. To fix it, leave the Integrated Environment and use the foll- owing lines to compile, link, and run; C>QCL NESTED.C /LINK /STACK:4000 C>NESTED Chapter 11 UNION1.C The bytes have ff in high order bits if the MSB of the byte is on. Refer to text about this. Chapter 13 BITOPS.C The bytes have ff in high order bits if the MSB of the byte is on. Chapter 14 All files These files were not compiled with this compiler, but should not require much work, if any, to compile since they follow the ANSI standard very closely as does this compiler. ***************** Mix C ver 1.0.0 ********************************* Mix Software 1132 Commerce Drive Richardson, TX 75081 (suggested floppy disk setup) Contents of drive A COMMAND.COM CCL.BAT (As listed below) EDIT.BAT (Your editor, whatever you use) STDIO.H (copied from STDIO on dist disk) RUNTIME.OVY (From your distribution disk) SMALCOM.OVY (From your distribution disk) CLIB.MIX (From your distribution disk) *.C (The files you wish to compile) Contents of drive B Exact copy of your MIX distribution disk (start of batch file used) REM MIX C COMPILER REM THE NEXT LINE CALLS WHATEVER FULL SCREEN EDITOR YOU USE EDIT %1.C B:CC %1 B:LINKER %1 %1 (End of batch file used) Note; The following problems were noted when compiling the files in chapters 1 to 13 with this compiler. The files in chapter 14 were not compiled with this compiler. Chapter 9 - SINGLEIO.C The system supplies a linefeed for you so it doesn't quite work like the book says. Chapter 9 - BETTERIN.C The system supplies a linefeed for you so it doesn't quite work like the book says. Chapter 13 - CHARCLAS.C Remove #include "ctype.h" from program. Chapter 13 - UPLOW.C Remove #include "ctype.h" from program. In addition, ENUM.C, BITFIELD.C, and all of the programs with prototyping may or may not work. We have no way to check since we have lost our copy of this compiler and we need to release this update of the tutorial.